-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Provide an interface for fuzzing sequence producer plugins #3551
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
terrelln
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Can you also add the documentation about how to build & run the fuzzer in seq_prod_fuzz_example/README.md?
|
Hi @embg, now only simple_round_trip is enabled, will other fuzzers be enabled in this PR or other new PRs? If other fuzzers are ready, could you @ me so that I can try them ASAP? |
|
@GarenJian-Intel Added support for the following fuzzers: Also, responded to all nits from @terrelln. Merging after CI passes. |
Fuzz-testing for the external sequence producer API was introduced in PR #3437. However, the setup in #3437 only allows fuzzers to exercise the implementation of the API on the libzstd side (the code in the core zstd library which interacts with a plugin). This PR allows us to fuzz the plugin code itself, which is a requirement for us to use plugins (such as hardware accelerators) in production.
Here is an example showing how this new interface allows us to link plugin code into the fuzzer build: